Add Janus to Development & Workflow - #500

Contribution check passed. @RamitVishwakarma, the required catalog checks passed.

Recommended: add scanner CI for security

This listing can merge without it. HOL still scans RamitVishwakarma/Janus independently.

We recommend including hashgraph-online/ai-plugin-scanner-action under .github/workflows/ on push and pull_request. It gives the project continuous security checks and improves the HOL Registry trust score shown by the trust badge.

Adding it:

• catches secrets, dangerous hooks, supply-chain issues, and other risky changes before they ship;
• removes the 10% trust-score reduction applied when maintainer scanner CI is missing, so the Registry badge reflects the full trust score;
• can surface findings in GitHub code scanning.

See SCANNER_GUIDE.md for the recommended workflow.

View the latest sweep.

Hey @RamitVishwakarma, your plugin is merged into the HOL catalog and ready to claim.

Claim your plugin

• Verify ownership of ramitvishwakarma/janus

Open the link and choose "Continue with GitHub". Use the GitHub account that maintains the repository. HOL requests only read:user and user:email. It does not request write access to the repository.

After verification, the listing gets an owner-verified badge, and the plugin dashboard shows its trust score, installs, and engagement.

Hi @RamitVishwakarma — a quick follow-up about your plugin ramitvishwakarma/janus.

The listing is live in the HOL Registry, and ownership verification is still available at HOL Guard.

Verify ownership with the GitHub account that owns the repository to unlock the owner-verified badge, plugin analytics, and the author dashboard. No repository write access is needed.

We may follow up again later if ownership verification is still incomplete.

If you already completed verification, no action is needed — the next scheduler run will stop these reminders.